Hello, Running two Exchange 2003 SP2 servers on WIN2K3 SP1 & 2. Receive the following error on one of our WIN2K3SP2 Exchange 2003 SP2 servers every three days & this cause the server to lock up & only a reboot resolves the problem - LDAP Bind was unsuccessful on directory achdcs002.hsa.co.uk for distinguished name ''. Directory returned error:[0x55] Timeout. Server was built three months ago to share our load of mailboxes & has been working fine until last week. The WIN2K3SP1 Exchange 2003 SP2 server is working without any problems. No DC's have recently been rebuilt so I can rule out Recipient Update Services fixes. Please see below the output from Netdiag - C:\Program Files\Support Tools>netdiag ....................................... Computer Name: ACHMSX003 DNS Host Name: achmsx003.hsa.co.uk System info : Windows 2000 Server (Build 3790) Processor : x86 Family 6 Model 23 Stepping 6, GenuineIntel List of installed hotfixes : KB924667-v2 KB925398_WMP64 KB925902 KB926122 KB927891 KB930178 KB931784 KB932168 KB933729 KB933854 KB935839 KB935840 KB936021 KB936357 KB936782 KB938127 KB938464 KB941569 KB941693 KB942830 KB942831 KB943055 KB943460 KB943485 KB944338-v2 KB944653 KB945553 KB946026 KB948496 KB948590 KB950762 KB950974 KB951072-v2 KB951698 KB951748 KB952954 KB953838 KB953838-IE7 KB953839 Q147222 Netcard queries test . . . . . . . : Passed Per interface results: Adapter : Local Area Connection Netcard queries test . . . : Passed Host Name. . . . . . . . . : achmsx003 IP Address . . . . . . . . : 10.0.10.33 Subnet Mask. . . . . . . . : 255.255.0.0 Default Gateway. . . . . . : 10.0.7.254 Primary WINS Server. . . . : 10.0.10.2 Secondary WINS Server. . . : 10.1.10.1 Dns Servers. . . . . . . . : 10.0.10.1 10.0.10.2 AutoConfiguration results. . . . . . : Passed Default gateway test . . . : Passed NetBT name test. . . . . . : Passed [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing. WINS service test. . . . . : Passed Global results: Domain membership test . . . . . . : Passed NetBT transports test. . . . . . . : Passed List of NetBt transports currently configured: NetBT_Tcpip_{84E15240-C4FE-4BC1-B80C-783DB8D1B0D3} 1 NetBt transport currently configured. Autonet address test . . . . . . . : Passed IP loopback ping test. . . . . . . : Passed Default gateway test . . . . . . . : Passed NetBT name test. . . . . . . . . . : Passed [WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined. Winsock test . . . . . . . . . . . : Passed DNS test . . . . . . . . . . . . . : Passed Redir and Browser test . . . . . . : Passed List of NetBt transports currently bound to the Redir NetBT_Tcpip_{84E15240-C4FE-4BC1-B80C-783DB8D1B0D3} The redir is bound to 1 NetBt transport. List of NetBt transports currently bound to the browser NetBT_Tcpip_{84E15240-C4FE-4BC1-B80C-783DB8D1B0D3} The browser is bound to 1 NetBt transport. DC discovery test. . . . . . . . . : Passed DC list test . . . . . . . . . . . : Passed Trust relationship test. . . . . . : Passed Secure channel for domain 'HSAGROUP' is to '\\achdcs001.hsa.co.uk'. Kerberos test. . . . . . . . . . . : Passed LDAP test. . . . . . . . . . . . . : Passed Bindings test. . . . . . . . . . . : Passed WAN configuration test . . . . . . : Skipped No active remote access connections. Modem diagnostics test . . . . . . : Passed IP Security test . . . . . . . . . : Skipped Note: run "netsh ipsec dynamic show /?" for more detailed information The command completed successfully C:\Program Files\Support Tools> I have tried the following - I had the same problem with one of my exchange servers and tried several different solutions. Pedro's post is correct and is the proper configuration when there multiple network interfaces on a single server. However, in my situation the network interface was listed first. By moving it down the list and clicking OK and then to the top of the list and clicking OK solved the LDAP Bind issue. Thank you for bringing this up Pedro. But has not resolved the problem. Any ideas?

Dear customer: From the following information, I found that your Exchange servers operating system is Windows 2000 Server, not WIN2K3SP2. Please double check it. Computer Name: ACHMSX003 DNS Host Name: achmsx003.hsa.co.uk System info: Windows 2000 Server (Build 3790) Also, inorder to better troubleshoot the issue, please help collect the following information: 1. On the problematic Exchange server 2003, open Event Viewer and right click application log, select clean all events, click yes when it promote you, 2. Open ESM, navigate to the problematic Exchange server 2003, right click it and select properties, click diagnostic logging tab, select MSExchangeAL, slect LDAP Operations category and increase logging level to maximum. Repeat this action for each category under MSExchangeAL. 3. Wait for the issue reoccurs, 4. On the problematic Exchange server 2003, open Event Viewer and save application log as .evt file and send it to v-rocwan@microsoft.com for analyze. 5. On achdcs002 domain contrlller, run dcdiag /v command and post the result into the forum for analyze. 6. On achdcs002 domain contrlller, open Event Viewer and save application log as .evt file and send it to v-rocwan@microsoft.com for analyze. Note: when you send e-mail to me, please let me know the subject of the post. Thanks for your cooperation. Rock Wang - MSFT

Resolved this matter by patching the problematic Exchange Server 2003 into a gig port on our switch. The server had a gig card installed which was set to auto but only patched into a 100MB port so network utilization was poor. By re-patching the server to a gig port Exchanger Server 2003 performance improved & no downtime has occured since.